Flow Sensor System

ABSTRACT

A system may include a disposable flow sensor and a base for the disposable flow sensor. A method may include scanning, with an optical scanner of the base for the disposable flow sensor, a flow sensor label attached to the disposable flow sensor to decode a flow sensor identifier associated with the flow sensor, scanning, with the optical scanner of the base for the disposable flow sensor, a patient label attached to a patient to decode a patient identifier associated with the patient, and connecting the disposable flow sensor to the base.

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional ApplicationSer. No. 62/966,291, entitled “Flow Sensor System”, filed Jan. 27, 2020,the entire disclosure of which is hereby incorporated by reference inits entirety.

BACKGROUND 1. Field

The present disclosure relates generally to a flow sensor system and, insome non-limiting embodiments or aspects, to a flow sensor system forsensing a flow of a fluidic medicament.

2. Technical Considerations

There is a need to reduce medication error at bedside during bolusdelivery. It is advantageous to provide a record of, and electronicallymeasure, bolus delivery which allows monitoring bolus delivery andautomatic documentation of bolus delivery as part of a patient's healthrecord. Additionally, it is advantageous to provide alerts when bolusdelivery inconsistent with a patient's medical record is about to occur.

SUMMARY

Non-limiting embodiments or aspects are set forth in the followingnumbered clauses:

Clause 1. A system including: a flow sensor including: a flow tubeincluding a fluid inlet at a first end of the flow tube, a fluid outletat a second end of the flow tube opposite the first end of the flowtube, a fluid injection port between the first end and the second end ofthe flow tube, and a valve configured to control a flow of a fluid inthe flow tube; at least one sensor configured to characterize at leastone attribute of the fluid in the flow tube; and a flow sensorelectrical contact in electrical communication with the at least onesensor; and a base configured to connect to the flow sensor, wherein thebase includes: one or more processors; a base electrical contact inelectrical communication with the one or more processors; a short rangewireless communication device; and a display, wherein the flow sensorelectrical contact is in electrical communication with the baseelectrical contact when the flow sensor is connected to the base.

Clause 2. The system of clause 1, wherein the valve is configuredtransition between a plurality of different states to control at leastone of: the flow of the fluid between the fluid inlet and the fluidoutlet, the flow of the fluid between the fluid inlet and the fluidinjection port, the flow of the fluid between the fluid injection portand the fluid outlet, or any combination thereof.

Clause 3. The system of any of clauses 1 and 2, wherein the one or moreprocessors are programmed and/or configured to automatically detect astate of the valve when the flow sensor is connected to the base.

Clause 4. The system of any of clauses 1-3, wherein the one or moreprocessors are programmed and/or configured to determine whether torecord information associated with the at least one attribute of thefluid in the flow tube based on the detected state of the valve.

Clause 5. The system of any of clauses 1-4, wherein the one or moreprocessors are programmed and/or configured to automatically detect aconnection of the flow sensor to the base.

Clause 6. The system of any of clauses 1-5, wherein the one or moreprocessors are programmed and/or configured to automatically detect aconnection of a syringe to the fluid injection port of the flow sensor.

Clause 7. The system of any of clauses 1-6, wherein the display includesa touchscreen display configured to receive user input from a user.

Clause 8. The system of any of clauses 1-7, wherein the flow sensor isinserted in-line with an IV line between a fluid source and a patient.

Clause 9. The system of any of clauses 1-8, wherein the short rangewireless communication device is configured to automatically communicatewith a short range wireless communication tag on a syringe via a shortrange wireless communication connection when the short range wirelesscommunication tag is brought within a communication range of the shortrange wireless communication device.

Clause 10. The system of any of clauses 1-9, wherein the short rangewireless communication device includes a near-field communication (NFC)receiver.

Clause 11. The system of any of clauses 1-10, wherein the base furtherincludes a wireless communication device configured to communicateinformation associated with the at least one attribute of the fluid inthe flow tube to a remote computing device.

Clause 12. The system of any of clauses 1-11, wherein the base furtherincludes an optical scanner configured to read a bar code label.

Clause 13. The system of any of clauses 1-12, wherein the base furtherincludes an opening configured to receive the flow sensor, and whereinthe flow sensor is configured for sliding engagement with the opening ofthe base.

Clause 14. A flow sensor, including: a flow tube including a fluid inletat a first end of the flow tube, a fluid outlet at a second end of theflow tube opposite the first end of the flow tube, a fluid injectionport between the first end and the second end of the flow tube, and avalve configured to control a flow of a fluid in the flow tube; at leastone sensor configured to characterize at least one attribute of thefluid in the flow tube; a flow sensor electrical contact in electricalcommunication with the at least one sensor.

Clause 15. The flow sensor of clause 14, wherein the valve is configuredtransition between a plurality of different states to control at leastone of: the flow of the fluid between the fluid inlet and the fluidoutlet, the flow of the fluid between the fluid inlet and the fluidinjection port, the flow of the fluid between the fluid injection portand the fluid outlet, or any combination thereof.

Clause 16. The flow sensor of any of clauses 14 and 15, wherein the flowsensor is inserted in-line with an IV line between a fluid source and apatient.

Clause 17. A base for a flow sensor, including: one or more processors;a base electrical contact in electrical communication with the one ormore processors; a short range wireless communication device; and adisplay, wherein the base sensor electrical contact is in electricalcommunication with at least one sensor of the flow sensor when the flowsensor is connected to the base.

Clause 18. The base of clause 17, wherein the one or more processors areprogrammed and/or configured to automatically detect a state of a valveof the flow sensor when the flow sensor is connected to the base.

Clause 19. The base of any of clauses 17 and 18, wherein the one or moreprocessors are programmed and/or configured to determine whether torecord information associated with at least one attribute of a fluidsensed by the flow sensor based on the detected state of the valve.

Clause 20. The base of any of clause 17-19, wherein the one or moreprocessors are programmed and/or configured to automatically detect aconnection of the flow sensor to the base.

Clause 21. The base of any of clauses 17-20, wherein the one or moreprocessors are programmed and/or configured to automatically detect aconnection of a syringe to the flow sensor.

Clause 22. The base of any of clauses 17-21, wherein the displayincludes a touchscreen display configured to receive user input from auser.

Clause 23. The base of any of clauses 17-22, wherein the short rangewireless communication device is configured to automatically communicatewith a short range wireless communication tag on a syringe via a shortrange wireless communication connection when the short range wirelesscommunication tag is brought within a communication range of the shortrange wireless communication device.

Clause 24. The base of any of clauses 17-23, wherein the short rangewireless communication device includes a near-field communication (NFC)receiver.

Clause 25. The base of any of clauses 17-24, wherein the base furtherincludes a wireless communication device configured to communicateinformation associated with the at least one attribute of the fluid inthe flow tube to a remote computing device.

Clause 26. The base of any of clauses 17-25, wherein the base furtherincludes an optical scanner configured to read a bar code label.

Clause 27. The base of any of clauses 17-26, wherein the base furtherincludes an opening configured to receive the flow sensor, and whereinthe flow sensor is configured for sliding engagement with the opening ofthe base.

Clause 28. A system including: a flow sensor including: a flow tubeincluding a fluid inlet at a first end of the flow tube, a fluid outletat a second end of the flow tube opposite the first end of the flowtube, a fluid injection port between the first end and the second end ofthe flow tube, wherein the fluid injection port extends from the flowtube in a first direction parallel to a longitudinal axis of the fluidinjection port; and a base configured to connect to the flow sensor,wherein the base includes: a short range wireless communication deviceincluding a curved coil antenna, wherein the curved coil antenna isradially curved with respect to the longitudinal axis of the fluidinjection port when the flow sensor is connected to the base.

Clause 29. The system of clause 28, wherein the curved coil antennaextends in the first direction parallel to the longitudinal axis of thefluid injection port.

Clause 30. The system of any of clauses 28-30, wherein the base furtherincludes a display, and wherein the curved coil antenna extends in adirection parallel to a plane defined by a face of the display.

Clause 31. The system of any of clauses 28-30, wherein the base furtherincludes a display, and wherein the curved coil antenna extends in adirection perpendicular to a plane defined by a face of the display.

Clause 32. The system of any of clauses 28-31, wherein the fluidinjection port is configured to connect to a syringe, and wherein, whenthe syringe is connected to the fluid injection port of the flow sensorand the flow sensor is connected to the base, the curved coil antenna isradially curved around the syringe.

Clause 33. The system of any of clauses 28-32, wherein a short rangewireless communication tag attached is attached to a body of thesyringe.

Clause 34. The system of any of clauses 28-33, wherein the short rangewireless communication device is configured to automatically communicatewith the short range wireless communication tag on the syringe via ashort range wireless communication connection when the short rangewireless communication tag is brought within a communication range ofthe short range wireless communication device.

Clause 35. The system of any of clauses 28-34, wherein the short rangewireless communication device receives information associated with amedication included in the syringe from the short range wirelesscommunication tag when the short range wireless communication tag isbrought within the communication range of the short range wirelesscommunication device.

Clause 36. The system of any of clauses 28-35, wherein the short rangewireless communication device includes a near-field communication (NFC)receiver.

Clause 37. A system including: a flow sensor including: a flow tubeincluding a fluid inlet at a first end of the flow tube, a fluid outletat a second end of the flow tube opposite the first end of the flowtube, a fluid injection port between the first end and the second end ofthe flow tube, wherein the fluid injection port is configured to connectto a syringe; and a base configured to connect to the flow sensor,wherein the base includes: a short range wireless communication deviceincluding a curved coil antenna, wherein, when the syringe is connectedto the fluid injection port of the flow sensor and the flow sensor isconnected to the base, the curved coil antenna is radially curved aroundthe syringe.

Clause 38. The system of clause 37, wherein the curved coil antennaextends in a first direction parallel to a longitudinal axis of thesyringe when the syringe is connected to the fluid injection port of theflow sensor and the flow sensor is connected to the base.

Clause 39. The system of any of clauses 37 and 38, wherein the basefurther includes a display, and wherein the curved coil antenna extendsin a direction parallel to a plane defined by a face of the display.

Clause 40. The system of any of clauses 37-39, wherein the base furtherincludes a display, and wherein the curved coil antenna extends in adirection perpendicular to a plane defined by a face of the display.

Clause 41. The system of any of clauses 27-40, wherein a short rangewireless communication tag attached is attached to a body of thesyringe.

Clause 42. The system of any of clauses 27-41, wherein the short rangewireless communication device is configured to automatically communicatewith the short range wireless communication tag on the syringe via ashort range wireless communication connection when the short rangewireless communication tag is brought within a communication range ofthe short range wireless communication device.

Clause 43. The system of any of clauses 27-42, wherein the short rangewireless communication device receives information associated with amedication included in the syringe from the short range wirelesscommunication tag when the short range wireless communication tag isbrought within the communication range of the short range wirelesscommunication device.

Clause 44. The system of any of clauses 27-43, wherein the short rangewireless communication device includes a near-field communication (NFC)receiver.

Clause 45. A base for a flow sensor, including: a housing including: anopening configured to receive the flow sensor; one or more processors; adisplay; and a short range wireless communication device including acurved coil antenna.

Clause 46. The base of clause 45, wherein the curved coil antennaextends in a direction parallel to a plane defined by a face of thedisplay.

Clause 47. The base of any of clauses 45 and 46, wherein the curved coilantenna extends in a direction perpendicular to a plane defined by aface of the display.

Clause 48. The system of any of clauses 45-47, wherein the curved coilantenna is radially curved around a syringe when the syringe isconnected to the flow sensor and the flow sensor is connected to thebase.

Clause 49. The system of any of clauses 45-48, wherein a short rangewireless communication tag attached is attached to a body of thesyringe.

Clause 50. The system of any of clauses 45-49, wherein the short rangewireless communication device is configured to automatically communicatewith the short range wireless communication tag on the syringe via ashort range wireless communication connection when the short rangewireless communication tag is brought within a communication range ofthe short range wireless communication device.

Clause 51. The system of any of clauses 45-50, wherein the short rangewireless communication device receives information associated with amedication included in the syringe from the short range wirelesscommunication tag when the short range wireless communication tag isbrought within the communication range of the short range wirelesscommunication device.

Clause 52. The system of any of clauses 45-51, wherein the short rangewireless communication device includes a near-field communication (NFC)receiver.

Clause 53. A method including: scanning, with an optical scanner of abase for a disposable flow sensor, a flow sensor label attached to thedisposable flow sensor to decode a flow sensor identifier associatedwith the flow sensor; scanning, with the optical scanner of the base forthe disposable flow sensor, a patient label attached to a patient todecode a patient identifier associated with the patient; connecting thedisposable flow sensor to the base.

Clause 54. The method of clause 53, further including: integrating thedisposable flow sensor into an IV line.

Clause 55. The method of any of clauses 53 and 54, wherein thedisposable flow sensor is integrated into the IV line before scanningthe flow sensor label, scanning the patient label, and connecting thedisposable flow sensor to the base.

Clause 56. The method of any of clauses 53-55, wherein the disposableflow sensor is integrated into the IV line after scanning the flowsensor label, scanning the patient label, and connecting the disposableflow sensor to the base.

Clause 57. The method of any of clauses 53-56, further including:communicating, with the base, the flow sensor identifier and the patientidentifier to a remote computing device; associating, with the remotecomputing device in a database, the flow sensor identifier with thepatient identifier.

Clause 58. The method of any of clauses 53-57, further including:communicating, with the base, to a remote computing device, a requestfor a status of the flow sensor associated with the flow sensoridentifier; receiving, with the base, from the remote computing device,an indication of the status of the flow sensor associated with the flowsensor identifier, wherein the indication of the status of the flowsensor includes an indication of whether the flow sensor identifier ofthe flow sensor is associated with the patient identifier of thepatient.

Clause 59. The method of any of clauses 53-58, further including:communicating, with the base, to the remote computing device, a baseidentifier associated with the base in the request for the status of theflow sensor associated with the flow sensor identifier; and associating,with the remote computing device in a database, the base identifier withthe flow sensor identifier and the patient identifier.

Clause 60. The method of any of clauses 53-59, further including:communicating, with the base, to the remote computing device, a requestfor information associated with the patient associated with the patientidentifier; receiving, with the base, from the remote computing device,the information associated with the patient; and displaying, with adisplay of the base, the information associated with the patient.

Clause 61. The method of any of clauses 53-60, wherein the informationassociated with the patient includes at least one of a list ofmedication allergies associated with the patient and a list ofmedication doses pending for the patient.

Clause 62. The method of any of clauses 53-61, further including:scanning, with a short range wireless communication device of the base,a short range wireless communication tag attached to a syringe to decodea medication identifier associated with a medication in the syringe;comparing, with the base, the medication identifier to the at least oneof the list of medication allergies associated with the patient and thelist of medication doses pending for the patient; and displaying, withthe display of the base, an alert associated with administration of themedication to the patient.

Clause 63. The method of any of clauses 53-62, wherein the short rangewireless communication device includes a near-field communication (NFC)receiver, and wherein the short range wireless communication tagincludes a NFC tag.

These and other features and characteristics of the present disclosure,as well as the methods of operation and functions of the relatedelements of structures and the combination of parts and economies ofmanufacture, will become more apparent upon consideration of thefollowing description and the appended claims with reference to theaccompanying drawings, all of which form a part of this specification,wherein like reference numerals designate corresponding parts in thevarious figures. It is to be expressly understood, however, that thedrawings are for the purpose of illustration and description only andare not intended as a definition of limits. As used in the specificationand the claims, the singular form of “a,” “an,” and “the” include pluralreferents unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

Additional advantages and details of embodiments or aspects of thepresent disclosure are explained in greater detail below with referenceto the exemplary embodiments that are illustrated in the accompanyingschematic figures, in which:

FIG. 1 is a diagram of non-limiting embodiments or aspects of anenvironment in which systems, devices, products, apparatus, and/ormethods, described herein, may be implemented;

FIG. 2 is a diagram of non-limiting embodiments or aspects of componentsof one or more devices and/or one or more systems of FIG. 1;

FIG. 3A is a flow chart of a non-limiting embodiment or aspect of aprocess for using a flow sensor system;

FIG. 3B is a flow chart of a non-limiting embodiment or aspect of aprocess for using a flow sensor system;

FIG. 3C is a flow chart of a non-limiting embodiment or aspect of aprocess for using a flow sensor system;

FIG. 3D is a flow chart of a non-limiting embodiment or aspect of aprocess for using a flow sensor system;

FIG. 3E is a flow chart of a non-limiting embodiment or aspect of aprocess for using a flow sensor system;

FIG. 3F is a flow chart of a non-limiting embodiment or aspect of aprocess for using a flow sensor system;

FIG. 3G is a flow chart of a non-limiting embodiment or aspect of aprocess for using a flow sensor system;

FIG. 3H is a flow chart of a non-limiting embodiment or aspect of aprocess for using a flow sensor system;

FIG. 4A is a perspective view of an implementation of non-limitingembodiments or aspects of a flow sensor system;

FIG. 4B is a perspective view of an implementation of non-limitingembodiments or aspects of a flow sensor system;

FIG. 4C is a perspective view of an implementation of non-limitingembodiments or aspects of a flow sensor system;

FIG. 4D is a perspective view of an implementation of non-limitingembodiments or aspects of a flow sensor system;

FIG. 5A is a perspective view of an implementation of non-limitingembodiments or aspects of a flow sensor system;

FIG. 5B is a perspective view of an implementation of non-limitingembodiments or aspects of a flow sensor system;

FIG. 5C is a perspective view of an implementation of non-limitingembodiments or aspects of a flow sensor system;

FIG. 6A is a perspective view of an implementation of non-limitingembodiments or aspects of a flow sensor system;

FIG. 6B is a perspective view of an implementation of non-limitingembodiments or aspects of a flow sensor system;

FIG. 6C is a perspective view of an implementation of non-limitingembodiments or aspects of a flow sensor system;

FIG. 7A is a perspective view of an implementation of non-limitingembodiments or aspects of a flow sensor system;

FIG. 7B is a perspective view of an implementation of non-limitingembodiments or aspects of a flow sensor system;

FIG. 8 is a diagram of an example magnetic H-field around an antenna ofa flow sensor system according to non-limiting embodiments or aspects;

FIG. 9A is a flowchart of non-limiting embodiments or aspects of aprocess for using a flow sensor system;

FIG. 9B is a flowchart of non-limiting embodiments or aspects of aprocess for using a flow sensor system;

FIG. 9C is a flowchart of non-limiting embodiments or aspects of aprocess for using a flow sensor system;

FIG. 9D is a flowchart of non-limiting embodiments or aspects of aprocess for using a flow sensor system;

FIG. 9E1 is a flowchart of non-limiting embodiments or aspects of aprocess for using a flow sensor system; and

FIG. 9E2 is a flowchart of non-limiting embodiments or aspects of aprocess for using a flow sensor system.

DETAILED DESCRIPTION

It is to be understood that the present disclosure may assume variousalternative variations and step sequences, except where expresslyspecified to the contrary. It is also to be understood that the specificdevices and processes illustrated in the attached drawings, anddescribed in the following specification, are simply exemplary andnon-limiting embodiments or aspects. Hence, specific dimensions andother physical characteristics related to the embodiments or aspectsdisclosed herein are not to be considered as limiting.

For purposes of the description hereinafter, the terms “end,” “upper,”“lower,” “right,” “left,” “vertical,” “horizontal,” “top,” “bottom,”“lateral,” “longitudinal,” and derivatives thereof shall relate to thepresent disclosure as it is oriented in the drawing figures. However, itis to be understood that the present disclosure may assume variousalternative variations and step sequences, except where expresslyspecified to the contrary. It is also to be understood that the specificdevices and processes illustrated in the attached drawings, anddescribed in the following specification, are simply exemplaryembodiments or aspects of the present disclosure. Hence, specificdimensions and other physical characteristics related to the embodimentsor aspects of the embodiments disclosed herein are not to be consideredas limiting unless otherwise indicated.

As used herein, proximal shall refer to a part or direction located awayor furthest from a patient (upstream), while distal shall refer to apart or direction towards or located nearest to a patient (downstream).Also, a drug substance is used herein in an illustrative, non-limitingmanner to refer to any substance injectable into the body of a patientfor any purpose. Reference to a patient may be to any being, human oranimal. Reference to a clinician may be to any person or thing givingtreatment, e.g., a nurse, doctor, machine intelligence, caregiver, oreven self-treatment.

No aspect, component, element, structure, act, step, function,instruction, and/or the like used herein should be construed as criticalor essential unless explicitly described as such. Also, as used herein,the articles “a” and “an” are intended to include one or more items, andmay be used interchangeably with “one or more” and “at least one.”Furthermore, as used herein, the term “set” is intended to include oneor more items (e.g., related items, unrelated items, a combination ofrelated and unrelated items, etc.) and may be used interchangeably with“one or more” or “at least one.” Where only one item is intended, theterm “one” or similar language is used. Also, as used herein, the terms“has,” “have,” “having,” or the like are intended to be open-endedterms. Further, the phrase “based on” is intended to mean “based atleast in partially on” unless explicitly stated otherwise.

As used herein, the terms “communication” and “communicate” refer to thereceipt or transfer of one or more signals, messages, commands, or othertype of data. For one unit (e.g., any device, system, or componentthereof) to be in communication with another unit means that the oneunit is able to directly or indirectly receive data from and/or transmitdata to the other unit. This may refer to a direct or indirectconnection that is wired and/or wireless in nature. Additionally, twounits may be in communication with each other even though the datatransmitted may be modified, processed, relayed, and/or routed betweenthe first and second unit. For example, a first unit may be incommunication with a second unit even though the first unit passivelyreceives data and does not actively transmit data to the second unit. Asanother example, a first unit may be in communication with a second unitif an intermediary unit processes data from one unit and transmitsprocessed data to the second unit. It will be appreciated that numerousother arrangements are possible.

It will be apparent that systems and/or methods, described herein, canbe implemented in different forms of hardware, software, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods are described herein without reference tospecific software code, it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Some non-limiting embodiments or aspects are described herein inconnection with thresholds. As used herein, satisfying a threshold mayrefer to a value being greater than the threshold, more than thethreshold, higher than the threshold, greater than or equal to thethreshold, less than the threshold, fewer than the threshold, lower thanthe threshold, less than or equal to the threshold, equal to thethreshold, etc.

As used herein, the term “computing device” or “computer device” mayrefer to one or more electronic devices that are configured to directlyor indirectly communicate with or over one or more networks. Thecomputing device may be a mobile device, a desktop computer, or thelike. Furthermore, the term “computer” may refer to any computing devicethat includes the necessary components to receive, process, and outputdata, and normally includes a display, a processor, a memory, an inputdevice, and a network interface. An “application” or “applicationprogram interface” (API) refers to computer code or other data sorted ona computer-readable medium that may be executed by a processor tofacilitate the interaction between software components, such as aclient-side front-end and/or server-side back-end for receiving datafrom the client. An “interface” refers to a generated display, such asone or more graphical user interfaces (GUIs) with which a user mayinteract, either directly or indirectly (e.g., through a keyboard,mouse, touchscreen, etc.).

As used herein, the term “server” may refer to or include one or moreprocessors or computers, storage devices, or similar computerarrangements that are operated by or facilitate communication andprocessing for multiple parties in a network environment, such as theInternet, although it will be appreciated that communication may befacilitated over one or more public or private network environments andthat various other arrangements are possible. Further, multiplecomputers, e.g., servers, or other computerized devices, directly orindirectly communicating in the network environment may constitute a“system”. As used herein, the term “data center” may include one or moreservers, or other computing devices, and/or databases.

As used herein, the term “mobile device” may refer to one or moreportable electronic devices configured to communicate with one or morenetworks. As an example, a mobile device may include a cellular phone(e.g., a smartphone or standard cellular phone), a portable computer(e.g., a tablet computer, a laptop computer, etc.), a wearable device(e.g., a watch, pair of glasses, lens, clothing, and/or the like), apersonal digital assistant (PDA), and/or other like devices. The terms“client device” and “user device,” as used herein, refer to anyelectronic device that is configured to communicate with one or moreservers or remote devices and/or systems. A client device or user devicemay include a mobile device, a network-enabled appliance (e.g., anetwork-enabled television, refrigerator, thermostat, and/or the like),a computer, and/or any other device or system capable of communicatingwith a network.

As used herein, the term “application” or “application programinterface” (API) refers to computer code, a set of rules, or other datasorted on a computer-readable medium that may be executed by a processorto facilitate interaction between software components, such as aclient-side front-end and/or server-side back-end for receiving datafrom the client. An “interface” refers to a generated display, such asone or more graphical user interfaces (GUIs) with which a user mayinteract, either directly or indirectly (e.g., through a keyboard,mouse, etc.).

Referring to FIG. 1, non-limiting embodiments or aspects of anenvironment 100 in which systems, devices, products, apparatus, and/ormethods, as described herein, may be implemented is shown. As shown inFIG. 1, environment 100 may include flow sensor system 150 includingflow sensor 160 and base 180, medical device 102 (e.g., a syringe, etc.)including short range wireless communication tag 104, IV line 106,communications network 108, and/or remote computing device 110.

Medical device 102 may be configured to physically connect to flowsensor 160 as described in more detail herein. Short range wirelesscommunication tag 104 may be attached to or integrated with medicaldevice 102 as described in more detail herein. In some non-limitingembodiments or aspects, short range wireless communication tag 104includes one or more computing devices, chips, contactless transmitters,contactless transceivers, NFC transmitters/receivers, RFIDtransmitters/receivers, contact based transmitters/receivers, and/or thelike. In some non-limiting embodiments or aspects, short range wirelesscommunication tag 104 can include one or more devices capable oftransmitting and/or receiving information to and/or from base 180 via ashort range wireless communication connection (e.g., a communicationconnection that uses NFC protocol, a communication connection that usesRadio-frequency identification (RFID), a communication connection thatuses a Bluetooth® wireless technology standard, and/or the like).Further details regarding non-limiting embodiments or aspects of medicaldevice 102 and short range wireless communication tag 104 are providedbelow with regard to FIGS. 3A-3H, 4A-4D, and 5A-5C.

Flow sensor 160 may be configured to be removably, physically, and/orelectrically connected to base 180 as described in more detail herein.In some non-limiting embodiments or aspects, flow sensor 160 may beconnected in-line with IV line 106 between a fluid source and a patient.Further details regarding non-limiting embodiments or aspects of flowsensor 160 are provided below with regard to FIGS. 3A-3H, 4A-4D, and5A-5C.

Base 180 may be configured to be removably, physically, and/orelectrically connected to flow sensor 160 as described in more detailherein. Base 180 may include may include one or more devices capable ofreceiving information and/or data from remote computing device 110(e.g., via communication network 108, etc.) and/or communicatinginformation and/or data to remote computing device 110 (e.g., viacommunication network 108, etc.). For example, base 180 may include acomputing device, a mobile device, and/or the like. In some non-limitingembodiments or aspects, base 180 includes one or more computing devices,chips, contactless transmitters, contactless transceivers, NFCtransmitters/receivers, RFID transmitters/receivers, contact basedtransmitters/receivers, and/or the like. In some non-limitingembodiments or aspects, base 180 can include one or more devices capableof transmitting and/or receiving information to and/or from short rangewireless communication tag 104 via a short range wireless communicationconnection (e.g., a communication connection that uses NFC protocol, acommunication connection that uses Radio-frequency identification(RFID), a communication connection that uses a Bluetooth® wirelesstechnology standard, and/or the like). In some non-limiting embodimentsor aspects, base 180 includes an integrated power source (not shown),such as a battery, and/or the like. Further details regardingnon-limiting embodiments or aspects of base 180 are provided below withregard to FIGS. 3A-3H, 4A-4D, and 5A-5C.

Communication network 108 may include one or more wired and/or wirelessnetworks. For example, communication network 108 may include a cellularnetwork (e.g., a long-term evolution (LTE) network, a third generation(3G) network, a fourth generation (4G) network, a fifth generationnetwork (5G) network, a code division multiple access (CDMA) network,etc.), a public land mobile network (PLMN), a local area network (LAN),a wide area network (WAN), a metropolitan area network (MAN), atelephone network (e.g., the public switched telephone network (PSTN)),a private network, an ad hoc network, an intranet, the Internet, a fiberoptic-based network, a cloud computing network, and/or the like, and/ora combination of these or other types of networks.

Remote computing device 110 may include one or more devices capable ofreceiving information and/or data from base 180 (e.g., via communicationnetwork 108, etc.) and/or communicating information and/or data to base180 (e.g., via communication network 108, etc.). For example, remotecomputing device 110 may include a computing device, a server, a groupof servers, a mobile device, a group of mobile devices, and/or the like.

The number and arrangement of devices and systems shown in FIG. 1 isprovided as an example. There may be additional devices and/or systems,fewer devices and/or systems, different devices and/or systems, ordifferently arranged devices and/or systems than those shown in FIG. 1.Furthermore, two or more devices and/or systems shown in FIG. 1 may beimplemented within a single device and/or system, or a single deviceand/or system shown in FIG. 1 may be implemented as multiple,distributed devices and/or systems. Additionally, or alternatively, aset of devices and/or systems (e.g., one or more devices or systems) ofenvironment 100 may perform one or more functions described as beingperformed by another set of devices and/or systems of environment 100.

Referring now to FIG. 2, FIG. 2 is a diagram of example components of adevice 200. Device 200 may correspond to base 180 and/or remotecomputing device 110. In some non-limiting embodiments or aspects, base180 and/or remote computing device 110 may include at least one device200 and/or at least one component of device 200. As shown in FIG. 2,device 200 may include bus 202, processor 204, memory 206, storagecomponent 208, input component 210, output component 212, and/orcommunication interface 214.

Bus 202 may include a component that permits communication among thecomponents of device 200. In some non-limiting embodiments or aspects,processor 204 may be implemented in hardware, firmware, or a combinationof hardware and software. For example, processor 204 may include aprocessor (e.g., a central processing unit (CPU), a graphics processingunit (GPU), an accelerated processing unit (APU), etc.), amicroprocessor, a digital signal processor (DSP), and/or any processingcomponent (e.g., a field-programmable gate array (FPGA), anapplication-specific integrated circuit (ASIC), etc.), and/or the like,which can be programmed to perform a function. Memory 206 may include arandom-access memory (RAM), a read only memory (ROM), and/or anothertype of dynamic or static storage device (e.g., a flash memory, amagnetic memory, an optical memory, etc.) that stores information and/orinstructions for use by processor 204.

Storage component 208 may store information and/or software related tothe operation and use of device 200. For example, storage component 208may include a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, etc.), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of computer-readable medium, along with acorresponding drive.

Input component 210 may include a component that permits device 200 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, amicrophone, etc.). Additionally, or alternatively, input component 210may include a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, an actuator, anNFC sensor, an RFID sensor, an optical sensor, a bar code reader etc.).Output component 212 may include a component that provides outputinformation from device 200 (e.g., a display, a speaker, one or morelight-emitting diodes (LEDs), etc.).

Communication interface 214 may include a transceiver-like component(e.g., a transceiver, a separate receiver and transmission source, etc.)that enables device 200 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. Communication interface 214 may permit device 200to receive information from another device and/or provide information toanother device. For example, communication interface 214 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface,and/or the like.

Device 200 may perform one or more processes described herein. Device200 may perform these processes based on processor 204 executingsoftware instructions stored by a computer-readable medium, such asmemory 206 and/or storage component 208. A computer-readable medium(e.g., a non-transitory computer-readable medium) is defined herein as anon-transitory memory device. A memory device includes memory spacelocated inside of a single physical storage device or memory spacespread across multiple physical storage devices.

Software instructions may be read into memory 206 and/or storagecomponent 208 from another computer-readable medium or from anotherdevice via communication interface 214. When executed, softwareinstructions stored in memory 206 and/or storage component 208 may causeprocessor 204 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, embodiments or aspects describedherein are not limited to any specific combination of hardware circuitryand software.

Memory 206 and/or storage component 208 may include data storage or oneor more data structures (e.g., a database, etc.). Device 200 may becapable of receiving information from, storing information in,communicating information to, or searching information stored in thedata storage or one or more data structures in memory 206 and/or storagecomponent 208.

The number and arrangement of components shown in FIG. 2 are provided asan example. In some non-limiting embodiments or aspects, device 200 mayinclude additional components, fewer components, different components,or differently arranged components than those shown in FIG. 2.Additionally, or alternatively, a set of components (e.g., one or morecomponents) of device 200 may perform one or more functions described asbeing performed by another set of components of device 200.

FIGS. 3A-3H, 4A-4D, and 5A-5C illustrate non-limiting embodiments oraspects of flow sensor system 150. Referring to FIGS. 3A-3H, 4A-4D, and5A-5C, flow sensor system 150 may include two main assemblies which fittogether prior to use: flow sensor 160 and base 180. In somenon-limiting embodiments or aspects, flow sensor 160 may be a single-useflow sensor which is engageable with reusable base 180.

Flow sensor system 150 may reduce medication error at bedside duringbolus delivery. Flow sensor system 150 may provide a record of andelectronically measure bolus delivery, which allows monitoring bolusdelivery and automatic documentation of bolus delivery as part of apatient's health record. Flow sensor system 150 may provide alerts whenbolus delivery inconsistent with a patient's medical record is about tooccur.

Flow sensor system 150 may be a handheld instrument Injection Site withinteractive interface for syringe injection IV drug delivery and directelectronic medical record documentation. Base 180 may include a durablereusable reader base with a touchscreen display and a separatedisposable consumable flow sensor 160.

In some non-limiting embodiments or aspects, flow sensor 160 may includea flow tube 162, at least one sensor 170 configured to characterize atleast one attribute of the fluid in the flow tube 162, and/or a flowsenor electrical contact 172 in electrical communication with the atleast one sensor 170. The flow tube 162 may include a fluid inlet 163 ata first end of the flow tube 162, a fluid outlet 164 at a second end ofthe flow tube 162 opposite the first end of the flow tube 162, a fluidinjection port 165 between the first end and the second end of the flowtube 162, and a valve 166 (e.g., a manual valve, etc.) configured tocontrol a flow of a fluid in the flow tube 162.

In some non-limiting embodiments or aspects, base 180 may include one ormore processors 204, a base electrical contact 192 in electricalcommunication with the one or more processors 204, a short rangewireless communication device (e.g., communication interface 214, anear-field communication (NFC) receiver, etc.), and/or a display 194(e.g., input component 210, output component 212, a touchscreen displayconfigured to receive user input from a user, etc.). The flow sensorelectrical contact 172 may be in electrical communication with the baseelectrical contact 192 when the flow sensor is connected (e.g.,connected, attached, mounted, etc.) to the base 180.

In some non-limiting embodiments or aspects, base 180 includes anopening 196 configured to receive the flow sensor 160, and the flowsensor 160 is configured for sliding engagement with the opening 196 ofthe base 180.

In some non-limiting embodiments or aspects, the at least one sensor 170may include a first ultrasonic transducer or piezo element 170 arrangedat an upstream position of the flow tube 162 and a second ultrasonictransducer or piezo element 170 is arranged at a downstream position ofthe flow tube 162. The first and second piezo elements 170 may beconfigured to transmit a flow signal indicative of a flow of a fluid(e.g., a fluidic medicament, etc.) in the flow tube 162. In somenon-limiting embodiments or aspects, the first ultrasonic transducer orpiezo element and the second ultrasonic transducer or piezo element 170are annular in shape and encircle the flow tube 162 at respectivemounting points. In some non-limiting embodiments or aspects, the firstultrasonic transducer or piezo element and the second ultrasonictransducer or piezo element 170 are mounted apart a pre-selecteddistance from each other. The first and second ultrasonic transducers orpiezeo elements 170 may be in electrical communication with the one ormore processors 204 (e.g., via the electrical contacts 172, 192, etc.)when the flow sensor 160 is connected to the base 180. For example, base180 may interact with the first and second ultrasonic transducers orpiezeo elements 170 in flow sensor 160 to measure displacement of fluidthrough the flow sensor 160.

In some non-limiting embodiments or aspects, valve 166 may be configuredtransition between a plurality of different states to control at leastone of: the flow of the fluid between the fluid inlet 163 and the fluidoutlet 164, the flow of the fluid between the fluid inlet 163 and thefluid injection port 165, the flow of the fluid between the fluidinjection port 165 and the fluid outlet 164, or any combination thereof.For example, valve 166 may include a 3-way stopcock valve, and/or thelike.

In some non-limiting embodiments or aspects, the one or more processors204 may be programmed and/or configured to automatically detect aconnection of flow sensor 160 to base 180. For example, when a userattaches flow sensor 160 to reader base 180, reader base 180automatically detects flow sensor 160 installation. As an example, amechanical button or switch on base 180 in electrical communication withthe one or more processors may be actuated by connection/disconnectionof flow sensor 160 to base 180 to send a signal to the one or moreprocessors 204 indicating the connection/disconnection state of flowsensor 160 to base 180.

In some non-limiting embodiments or aspects, the one or more processors204 are programmed and/or configured to automatically detect aconnection of a syringe 102 to the fluid injection port 165 of the flowsensor 160. For example, when a user inserts a syringe 102 with needlefree Luer connector into fluid injection port 165, reader base 180 mayautomatically detect the connection of the syringe to the fluidinjection port 165 syringe presence and initiates decoding of tag 104(e.g., via the short range wireless communication device, etc.) torecord information contents of tag 104 (e.g., medication information,etc.). As an example, flow sensor system 150 may include an electronicand mechanical interface that interacts with the syringe 102 wheninserted into fluid injection port 165 to detect the presence of thesyringe 102 upon insertion by the user. In such an example, a mechanicalbutton or switch on flow sensor 160 in electrical communication with theone or more processors (e.g., via the electrical contacts 172 and 192,etc.) may be actuated by connection/disconnection syringe 102 to fluidinjection port 165 to send a signal to the one or more processors 204indicating the connection/disconnection state of syringe 102 to fluidinjection port 165. In some non-limiting embodiments or aspects, tag orlabel 104, which may include an NFC tag embedded in the tag or label104, may be manually placed on a body of syringe 102 using a standardlabel printer. For example, a label printer can be used to encode theNFC tag at the time of printing. Additionally or alternatively, NFCencoding can be performed using a separate NFC tag encoding unit.

In some non-limiting embodiments or aspects, the short range wirelesscommunication device is configured to automatically communicate with theshort range wireless communication tag 104 on syringe 102 via a shortrange wireless communication connection when the short range wirelesscommunication tag 104 is brought within a communication range of theshort range wireless communication device. In some non-limitingembodiments or aspects, the short range wireless communication device isconfigured to automatically communicate with the short range wirelesscommunication tag 104 on the syringe 102 via a short range wirelesscommunication connection in response to the base 180 detecting aconnection of the syringe 102 to the fluid injection port 165. Forexample, the tag 104 may be detected by using NFC when placed radiallyadjacent to an antenna of the short range wireless communication devicein base 180. As an example, base 180 may include an integrated NFCantenna positioned radially to record syringe label tag 104 and read anddecode encoded information therefrom. In such an example, the NFCantenna and label tags are optimized to eliminate false detection ofadjacently positioned syringes with NFC tag labels (e.g., an NFC antennamounted radially in the base 180 and label tag 104 on the syringe barrelof syringe 102 can be used to transmit encoded label information fromthe syringe label tag 104 to the reader base 180, etc.).

In some non-limiting embodiments or aspects, the one or more processors204 may be programmed and/or configured to automatically detect a stateof the valve 166 when the flow sensor 160 is connected to the base 180.For example, base 180 may automatically determine a state or position ofvalve 166 when a user manually switches the state or position of thevalve 166. As an example, an electronic and/or mechanical interface mayinteract with the valve 166 to monitor valve position or state. In suchan example, a mechanical button or switch on flow sensor 160 inelectrical communication with the one or more processors (e.g., via theelectrical contacts 172 and 192, etc.) may be actuated by changing theposition or state of the valve 166 to send a signal to the one or moreprocessors 204 indicating the state or position of the valve 166 (e.g.,indicating that fluid flow is allowed between the fluid inlet 163 andthe fluid outlet 164, between the fluid inlet 163 and the fluidinjection port 165, between the fluid injection port 165 and the fluidoutlet 164, or any combination thereof, etc.).

In some non-limiting embodiments or aspects, the one or more processors204 are programmed and/or configured to determine whether to recordinformation associated with the at least one attribute of the fluid inthe flow tube 162 based on the detected state of the valve 166. Forexample, a user may switch the state or position of the valve 166 toenable recording of flow measurement and/or permit IV fluid flow. As anexample, the one or more processors 204 of base 180 may determine whento bookmark flow measurements and ignore IV fluid flow and redundantvolume measurements when IV fluid is drawn into the syringe 102 thensubsequently injected through the flow sensor 160.

In some non-limiting embodiments or aspects, flow sensor 160 is insertedin-line with IV line 106 between a fluid source and a patient. Forexample, disposable flow sensor 160 can be inserted in-line with IV line106 enabling IV fluid to pass directly to a patient extension linecatheter. In some non-limiting embodiments or aspects, valve 166 isconfigured to enable syringe 102 to draw IV fluid from IV line 106 anddeliver the drawn IV fluid through the flow sensor 160 to push the fluidto flush the flow sensor 160 and extension line of a previouslydelivered drug volume. In some non-limiting embodiments or aspects, flowsensor 160 may be integrated into IV 106 (e.g., into an IV extension setline, etc.) without separate detachable connectors. In some non-limitingembodiments or aspects, fluid flow stopcock valves can be positionedin-line before and/or after flow sensor 160 and/or additionalfunctionality to incorporate workflow operations can be developed withinthe interactive display 194 of base 180. For example, by positioningflow sensor 160 in-line with IV line 106, a dead space issue to due lackof flushing associated with parallel connections can be resolved.

In some non-limiting embodiments or aspects, base 180 includes anoptical scanner configured to read a bar code label (e.g., a patientwristband bar code label, a bar code label on flow sensor 160, etc.).

In some non-limiting embodiments or aspects, display 194 includes atouchscreen display configured to receive user input from a user. Forexample display 194 may include an interactive graphical user interfaceconfigured to display a current status of internal functions of readerbase 180, a current status of an injection site, and/or a prompt foruser interaction, and reader base 180 may interact with the user viatouchscreen display, audio, voice command, haptic feedback, and/or thelike (e.g., to prompt the user on current status and request user input,etc.). Accordingly, by incorporating display 194 into base 180, a userneed not remove their attention from the base 180 to interact with thedisplay 194.

In some non-limiting embodiments or aspects, base 180 includes awireless communication device configured to communicate informationassociated with the at least one attribute of the fluid in the flow tube162 to remote computing device 110. For example, base 180 maycommunicate information and/or data with remote computing device 110 todocument drug delivery occurrences into patient medical records (e.g.,patient medical records associated with a patient wristband bar codelabel scanned by the optical scanner of base 180, etc.).

Referring now to FIGS. 4A, 5A, 6A-6C, 7A, 7B, and 8, in somenon-limiting embodiments or aspects, short range wireless communicationdevice of base 180 may include a curved coil antenna 600.

A size of syringe 102 may vary (e.g., a syringe size may be in a rangefrom 1 mL to 60 mL, etc.). A location of short range wirelesscommunication tag 104 on syringe 102 may vary. For example, a user mayattach short range wireless communication tag 104 at various differentlocations on a body of syringe 102. The variability between location ofthe tag 104 and the size of the syringe 102 in combination with acurvature of the body syringe 102 may make reading encoded data off oftag 104 more difficult and/or put considerable burden on a user. Forexample, HF RFID/NFC works by creating an inductive coupling of magneticwaves in the 13.56 MHz range to power up a HF RFID/NFC tag, whichtransmits the encoded information back to a transmitting coil antenna.As an example, the transmitting coil antenna should transmit enoughenergy to power up the tag 104, and a tag coil antenna in tag 104 shouldreceive enough energy to power up and transmit the encoded informationstored in tag 104 back to the transmitting coil antenna. A transmittingcoil antenna may be flat and the tag 104 may lie parallel to thetransmitting coil antenna to power the tag 104 up if the tag 104receives enough energy. The energy received may be based a distance ofthe tag 104 to the transmitting coil antenna and/oe an orientation ofthe transmitting coil antenna with respect to the tag 104 (e.g., anoffset and/or an angle at which the tag 104 faces the transmitting coilantenna, etc.). For example, as the angle between the coil antenna ofthe tag 104 and the transmitting coil antenna becomes closer to 90 or270 degrees, antenna energy received by tag 104 may be reduced to zero.As an example, a formula for calculating an amount of energy received bytag 104 from a transmitting coil antenna may be defined according aCOSINE(angle). Accordingly, if the angle between the transmitting coilantenna and the coil antenna of the tag 104 reaches 90 or 270 degrees,the energy received by the tag 104 is zero and the tag 104 cannot powerup. In this way, if tag 104 is on a syringe 102 and the tag 104 can beplaced anywhere on the syringe 102 by a user, there is a possibilitythat the angle may be close enough to or at the 0 energy point wheredata encoded in the tag 104 cannot be read by a short range wirelesscommunication device.

Non-limiting embodiments or aspects of flow sensor system 150 includingcurved coil antenna 600 may reduce and/or eliminate a 90 and/or 270degree angle between a transmitting coil antenna of the short rangewireless communication device of base 180 and tag 104 on syringe 102 byencompassing and/or surrounding syringe 102 with the curved coil antenna600. For example, and referring to FIG. 8, curved coil antenna 600 mayenable magnetic waves to be transmitted out from the short rangewireless communication device of base 180 in a radial fashion withrespect to syringe 102 when syringe 102 is connected to flow sensor 160and flow sensor 160 is connected to base 180, thereby covering a largerarea of syringe 102 (e.g., depending on a circumferential area of thecurved coil antenna 600, an acceptance criteria for successful reads,etc.). As an example, curved coil antenna 600 may enable the magneticwaves to be transmitted radially from the short range wirelesscommunication device of base 180 to encompass an NFC HF RFID tag on acircular syringe. In contrast, a flat NFC coil antenna may result in themagnetic waves being transmitted orthogonal to the coil antenna, whichmay result in an NFC HF RFID tag that does not line up with thetransmitted magnetic waves (e.g., particularly if the tag is 90 degreesto the waves, etc.) not powering up and not transmitting backinformation encoded on the tag to the transmitting NFC coil antenna.Accordingly, a curved NFC coil antenna may enable magnetic waves to betransmitted in more directions with respect to an NFC HF RFID tag (e.g.,for NFC communications based on the NFC standards of ISO14443 and/orISO15693 which describe physical layer technology and protocol layertechnology, etc.), thereby reducing and/or preventing a 90 and/or 270degree angle between the transmitting coil antenna and the tag.

In some non-limiting embodiments or aspects, fluid injection port 165 offlow sensor 160 may extend from flow tube 162 in a first directionparallel to a longitudinal axis of the fluid injection port 165, andcurved coil antenna 600 in the short range wireless communication deviceof base 180 may be radially curved with respect to the longitudinal axisof the fluid injection port 165 when the flow sensor 160 is connected tothe base 180. For example, fluid injection port 165 may be configured toconnect to syringe 102 and, when the syringe 102 is connected to thefluid injection port 165 of the flow sensor 160 and the flow sensor 160is connected to the base 180, curved coil antenna 600 may be radiallycurved around the syringe 102 and/or extend in the first directionparallel to the longitudinal axis of the fluid injection port 165.

In some non-limiting embodiments or aspects, as shown for example inFIGS. 4A and 6A-6C, curved coil antenna 600 extends in a directionparallel to a plane defined by a face of display 194 of base 180 (e.g.,in a direction parallel to a longitudinal axis of syringe 102 whensyringe 102 is connected to flow sensor 160 and flow sensor 160 isconnected to base 180, etc.). In some non-limiting embodiments oraspects, as shown for example in FIG. 5A, curved coil antenna 600extends in a direction not parallel (e.g., in a direction perpendicularto) a plane defined by a face of display 194 of base 180 (e.g., in adirection perpendicular to a longitudinal axis of syringe 102 whensyringe 102 is connected to flow sensor 160 and flow sensor 160 isconnected to base 180, etc.). In such example, curved coil antenna 600may at least partially surround syringe 102 when syringe 102 isconnected to flow sensor 160 and flow sensor 160 is connected to base180. In some non-limiting embodiments or aspects, a curvature of curvedcoil antenna may correspond to a circumferential area of a 60 mLsyringe, and/or the like.

Referring now to FIGS. 3A-3H and 9A-9E, FIGS. 3A-3H and 9A-9E areflowcharts of non-limiting embodiments or aspects of processes for usinga flow sensor system. In some non-limiting embodiments or aspects, oneor more of the steps of the processes are performed (e.g., completely,partially, etc.) by flow sensor system 150 (e.g., one or more devices offlow sensor system 150, etc.). In some non-limiting embodiments oraspects, one or more of the steps of the processes are performed (e.g.,completely, partially, etc.) by another device or a group of devicesseparate from or including flow sensor system 150, such as remotecomputing device 110 (e.g., one or more devices of a system of remotecomputing device 110, etc.).

As shown in FIG. 9A, at step WS5.2, a process for using a flow sensorsystem includes scanning a flow sensor label attached to the disposableflow sensor to decode a flow sensor identifier associated with the flowsensor. For example, an optical scanner of base 180 (e.g., “Reader” inFIGS. 9A-9E) for disposable flow sensor 160 (e.g., “Sensor” in FIGS.9A-9E) may scan a flow sensor label (e.g., a flow sensor barcode, etc.)attached to the disposable flow sensor to decode a flow sensoridentifier associated with the flow sensor. As an example, barcodescanning of the disposable flow sensor 160 enables base 180 (and/orremote computing system 110) to determine whether the disposable florsensor 160 has been used yet or not and, if so, by which patient.

As shown in FIG. 9A, at step WS4, a process for using a flow sensorsystem includes scanning a patient label attached to a patient to decodea patient identifier associated with the patient. For example, theoptical scanner of base 180 for disposable flow sensor 160 may scan apatient label attached to a patient (e.g., a patient wristband, apatient barcode, etc.) to decode a patient identifier associated withthe patient. As an example, a smart device (e.g., base 180, etc.) may beutilized to electronically scan, with, for example, a barcode scanner,each of a smart IV consumable (e.g., disposable flow sensor 160, etc.)and the patient wristband provided by an EMR vendor. The smart devicemay communicate patient identifier information (e.g., Patient MRN) andsmart IV consumable unique identification number up to a virtual server(e.g., remote computing device 110, etc.) on a hospital network. Thevirtual server may utilize patient identifier information to generate abi-directional link to applications on the Hospital Information Systemassociated to that patient relevant to the function of the smart deviceand smart consumable. Once the bi-directional link is established, thevirtual server may associate the link to the smart IV consumable uniqueidentification number and, if the smart device is disassociated, thesmart device, or a new different device, can be re-associated by a scanof the smart consumable. In contrast, if the patient is associated bythe electronics alone, such as a patient association to a barcodereader, if that device can no longer be used (e.g., runs out ofbatteries, etc.) re-association by scanning the patient wristband isrequired and, if the wristband is not accessible (e.g., during surgery,etc.), manual entry of the patient identifier may need to be performed,which may be subject to error. For example, a device may need to beassociated with a patient record by having the case assigned to thedevice by the EMR, manually selecting the patient through the userinterface on the device or associating the smart device directly to thepatient through electronic scan or otherwise. Further, if not properlydisassociated, a device may also be at risk of utilization on theincorrect patient recording information to the wrong patient record.

As shown in FIG. 9A, at step WS5.3, a process for using a flow sensorsystem includes connecting the disposable flow sensor to the base. Forexample, disposable flow sensor 160 may be connected to base 180.

As shown in FIG. 9A, at step WS5.1, a process for using a flow sensorsystem includes integrating the disposable flow sensor into an IV line.For example, disposable flow sensor 160 may be integrated into IV line106.

In some non-limiting embodiments or aspects, and referring now to FIG.9B, disposable flow sensor 160 is integrated into IV line 106 beforescanning the flow sensor label, scanning the patient label, andconnecting the disposable flow sensor 160 to the base 180. For example,integrating disposable flow sensor 160 into IV line 106 before scanningthe flow sensor label, scanning the patient label, and connecting thedisposable flow sensor 160 to the base 180 may enable a clinician toassociate the patient when performing other positive patientidentification and/or to scan and attach the disposable flow sensor 160in one more contiguous step which adds value, for example, when settingup a patient for a procedure in an operating room. As an example,scanning the patient ID prior to connecting may ensure that the IV line106 does not hinder a user in scanning the patient ID, which may beideal for outpatients where a new IV line is built with the disposableflow sensor 160 in place for the procedure.

In some non-limiting embodiments or aspects, and referring now to FIG.9C, disposable flow sensor 160 is integrated into IV line 106 afterscanning the flow sensor label, scanning the patient label, andconnecting the disposable flow sensor 160 to the base 180. For example,integrating disposable flow sensor 160 into IV line 106 after scanningthe flow sensor label, scanning the patient label, and connecting thedisposable flow sensor 160 to the base 180 may enable a clinician toprepare the base 180 and disposable flow sensor 160 prior to interactionwith a patient and/or a pre-existing IV, which may add value when theclinician has time prior to the arrival of an inpatient with apre-existing IV saving steps that need not be performed in the presenceof the patient.

As shown in FIG. 9A, at steps WS4, WS5.2, and/or WS5.4, a process forusing a flow sensor system includes communicating the flow sensoridentifier and the patient identifier to a remote computing device andassociating the flow sensor identifier with the patient identifier. Forexample, base 180 may communicate the flow sensor identifier and thepatient identifier to remote computing device 110, and remote computingdevice 110 may associate the flow sensor identifier with the patientidentifier in a database.

In some non-limiting embodiments or aspects, and referring now to FIG.9D, base 180 may communicate, to remote computing device 110, a requestfor a status of the disposable flow sensor 160 associated with the flowsensor identifier and receive, from remote computing device 110, anindication of the status of the disposable flow sensor 160 associatedwith the flow sensor identifier. For example, the indication of thestatus of the disposable flow sensor 160 may include an indication ofwhether the flow sensor identifier of the disposable flow sensor 160 isassociated with the patient identifier of the patient.

In some non-limiting embodiments or aspects, and still referring to FIG.9D, base 180 may communicate, to remote computing device 110, a baseidentifier associated with the base 180 in the request for the status ofthe disposable flow sensor 160 associated with the flow sensoridentifier, and remote computing device 110 may associate the baseidentifier with the flow sensor identifier and the patient identifier.

As shown in FIG. 9A, at steps WS4 and/or WS6, a process for using a flowsensor system includes communicating a request for informationassociated with the patient associated with the patient identifier,receiving the information associated with the patient, and displayingthe information associated with the patient. For example, and referringalso to FIG. 9E, base 180 may communicate, to remote computing device110, a request for information associated with the patient associatedwith the patient identifier, receive, from remote computing device 110,the information associated with the patient, and display, with adisplay, the information associated with the patient.

In some non-limiting embodiments or aspects, the information associatedwith the patient includes at least one of a list of medication allergiesassociated with the patient and a list of medication doses pending forthe patient.

In some non-limiting embodiments or aspects, and still referring to FIG.9E, a short range wireless communication device of base 180 may scan ashort range wireless communication tag 104 attached to a syringe 102 todecode a medication identifier associated with a medication in thesyringe 102, and the base 180 may compare the medication identifier tothe at least one of the list of medication allergies associated with thepatient and the list of medication doses pending for the patient. Forexample, a display 194 of the base 180 may display an alert associatedwith administration of the medication to the patient based on thecomparison. In some non-limiting embodiments or aspects, the short rangewireless communication device includes a near-field communication (NFC)receiver, and wherein the short range wireless communication tagincludes a NFC tag.

Accordingly, non-limiting embodiments or aspects of a process for usinga flow sensor system may enable more steps to be performed at ae site ofcare with a patient in view which provides advantages over methods thatrequire interaction with EMR screens. Further, non-limiting embodimentsor aspects of a process for using a flow sensor system may enable apatient to be associated with the smart consumable that is attached tothe patient IV line rather than the electronics (e.g., base 180, etc.)alone, which provides for higher confidence that the device data islinked to the proper patient as the smart IV consumable is directlyattached to the patient (through the IV), and which may enable the smartdevice to be swapped with another that can be associated to the patientby a scan of the smart consumable as opposed to being required tore-scan the patient wristband.

Although embodiments or aspects have been described in detail for thepurpose of illustration and description, it is to be understood thatsuch detail is solely for that purpose and that embodiments or aspectsare not limited to the disclosed embodiments or aspects, but, on thecontrary, are intended to cover modifications and equivalentarrangements that are within the spirit and scope of the appendedclaims. For example, it is to be understood that the present disclosurecontemplates that, to the extent possible, one or more features of anyembodiment or aspect can be combined with one or more features of anyother embodiment or aspect. In fact, any of these features can becombined in ways not specifically recited in the claims and/or disclosedin the specification. Although each dependent claim listed below maydirectly depend on only one claim, the disclosure of possibleimplementations includes each dependent claim in combination with everyother claim in the claim set.

What is claimed is:
 1. A method comprising: scanning, with an opticalscanner of a base for a disposable flow sensor, a flow sensor labelattached to the disposable flow sensor to decode a flow sensoridentifier associated with the flow sensor; scanning, with the opticalscanner of the base for the disposable flow sensor, a patient labelattached to a patient to decode a patient identifier associated with thepatient; and connecting the disposable flow sensor to the base.
 2. Themethod of claim 1, further comprising: integrating the disposable flowsensor into an IV line.
 3. The method of claim 2, wherein the disposableflow sensor is integrated into the IV line before scanning the flowsensor label, scanning the patient label, and connecting the disposableflow sensor to the base.
 4. The method of claim 2, wherein thedisposable flow sensor is integrated into the IV line after scanning theflow sensor label, scanning the patient label, and connecting thedisposable flow sensor to the base.
 5. The method of claim 1, furthercomprising: communicating, with the base, the flow sensor identifier andthe patient identifier to a remote computing device; and associating,with the remote computing device in a database, the flow sensoridentifier with the patient identifier.
 6. The method of claim 1,further comprising: communicating, with the base, to a remote computingdevice, a request for a status of the flow sensor associated with theflow sensor identifier; and receiving, with the base, from the remotecomputing device, an indication of the status of the flow sensorassociated with the flow sensor identifier, wherein the indication ofthe status of the flow sensor includes an indication of whether the flowsensor identifier of the flow sensor is associated with the patientidentifier of the patient.
 7. The method of claim 6, further comprising:communicating, with the base, to the remote computing device, a baseidentifier associated with the base in the request for the status of theflow sensor associated with the flow sensor identifier; and associating,with the remote computing device in a database, the base identifier withthe flow sensor identifier and the patient identifier.
 8. The method ofclaim 1, further comprising: communicating, with the base, to the remotecomputing device, a request for information associated with the patientassociated with the patient identifier; receiving, with the base, fromthe remote computing device, the information associated with thepatient; and displaying, with a display of the base, the informationassociated with the patient.
 9. The method of claim 8, wherein theinformation associated with the patient includes at least one of a listof medication allergies associated with the patient and a list ofmedication doses pending for the patient.
 10. The method of claim 9,further comprising: scanning, with a short range wireless communicationdevice of the base, a short range wireless communication tag attached toa syringe to decode a medication identifier associated with a medicationin the syringe; comparing, with the base, the medication identifier tothe at least one of the list of medication allergies associated with thepatient and the list of medication doses pending for the patient; anddisplaying, with the display of the base, an alert associated withadministration of the medication to the patient.
 11. The method of claim10, wherein the short range wireless communication device includes anear-field communication (NFC) receiver, and wherein the short rangewireless communication tag includes a NFC tag.